STARS Implementation Guide
0.6.1 - release

This page is part of the Csiro Stars (v0.6.1: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

Home

Official URL: https://starsapi.csiro.au/fhir-ig/stars/ImplementationGuide/csiro.stars Version: 0.6.1
Computable Name: CsiroStars

CSIRO logo

Introduction

The STARS Implementation Guide provides a consistent framework for eRequesting and result delivery across the STARS network of laboratories. This enables data exchange between systems based on the FHIR (Fast Health Interoperability Resources) specification. This guide outlines the specifications required to conform to this standard.

The STARS network was originially formed in 2012 as a method to steamline bulk specimen requests.

This verison is based of R5.0.0 release of the FHIR specification.

Message Format

The message format has been refreshed and is based on the open FHIR standard as is being rapidly adopted in the health and laboratory space to increase compatibility and interconnection between systems. The STARS network runs as a hub and spoke service with clients polling for new messages. This is a FHIR-like service api and messages use FHIR Bundle Message format (Bundle.type = message). These are self contained FHIR resources as outlined in this guide that encapsulate the individual FHIR components in a single request as a self-contained message.

A typical STARS Bundle includes:

  • A Bundle resource (root)
  • One or more entry elements, each containing
    • resource (eg. ServiceRequest, DiagnosticReport, Task or other supporting types)
    • Resources MUST be self-contained and fully resolvable within the bundle
    • Identifiers SHOULD be flobally unique where possible
    • Profiles defined by STARS MUST be applied to each resource

    See the HL7 FHIR site for further details.

Workflow

The workflow consists of three primary elements:

STARS Message WorkflowRequesting LaboratoryRequesting LaboratoryTesting LaboratoryTesting LaboratoryRequest with specimen testing request (Bundle-ServiceRequest)Request received, submission paperwork attached (Bundle-Task-RequestReceived)Specimen received (Bundle-Task-SpecimenReceived)Report results (Bundle-DiagnosticReport)
Send specimen to Lab, receive results from testing

STARS Api

The Direct api connection is the preferred method for better integration of your LIMS and day to day processes.

STARS Client

The legacy stars-client has been refreshed inline with the stars-api project. This may be used as a transition while further direct api integration is being explored. Using this client will involve modifying your current export process to map to the new fields and values. See the Migration Guide for further direction.

Terminology

The FHIR system is built to take advantage of standardised terminology lists hosted on an ontology server.

A dedicated Ontoserver has been implemented for the purpose of creating and hosting custom user codesystems and value sets. This will be utilised for developing concept maps linked to standardised terminology lists (e.g. SNOMED, LONIC).

Initial setup of the Ontoserver will take advantage of the exisiting STARS legacy terminology sets as the core of the terminology server.

Downloads

downloads

FHIR Shorthand Resources

This guide has been automatically built using FHIR Shorthand to define a standard set of required fields that form a profile schema for specimen transmission.

HL7 Confluence site

FHIR Shorthand Documentation

FHIR Shorthand documentation code repository

SUSHI code repository

Zulip channel: #shorthand

Dependencies

IGPackageFHIRComment
.. STARS Implementation Guidecsiro.stars#0.6.1R5
... HL7 Terminology (THO)hl7.terminology.r5#7.1.0R5Automatically added as a dependency - all IGs depend on HL7 Terminology
.... FHIR Extensions Packhl7.fhir.uv.extensions.r5#5.2.0R5
... FHIR Tooling Extensions IGhl7.fhir.uv.tools.r5#1.1.2R5for example references

Package hl7.fhir.uv.extensions.r5#5.2.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.uv.tools.r5#1.1.2

This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00)

Cross Version Analysis

IP Statements

This publication includes IP covered under the following statements.